This repository was archived by the owner on May 12, 2020. It is now read-only.
Support exporting dumps with custom user-defined CLI args #162
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi there!
My use case is to export without owner or privileges statements, and also to export to a directory instead of a SQL file. But I notice the
PostgresProcess#export*ToFileutility methods do not support such capabilities, unlike what is done in thePostgresProcess#importFromFileWithArgsmethod.This PR attempts to generalize that idea by supporting any user-defined custom arguments, provided they are compliant with the already existing default options passed to pg_dump.
Thanks.